home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Just Call Me Internet
/
Just Call Me Internet.iso
/
com
/
othernet
/
fidonet
/
checktic
/
readme.eng
< prev
Wrap
Text File
|
1994-10-04
|
4KB
|
104 lines
CHECKTIC
Version 1.0.1 - October 4th, 1994
workaround for TICKer-ST v.1.04beta from Rayko Balun
for the CRC-checksum-comparison-function
from Markus Fischer
EMail-address: FidoNet: 2:2410/204.0
NeST: 90:400/303.0
WHAT'S THIS PROGRAM FOR?
Everyone using TICKer-ST from Rayko Balun has obviously noticed
that it has some problems with TIC-files with a CRC-checksum
containing a leading zero. They are handled as having a bad
checksum and left with the accompaning file in the inbound-
folder. So the sysop has to do some additional work to remove the
"garbage". As I hate this work I've written this little program,
so it has to be done more seldom than without it.
LEGAL WORKS AND DISCLAIMER
The use of the program is free. I'd like to get a feedback from
those using it, so please send a netmail to one of my adresses
above. Please do report bugs or suggestions via netmail too.
Distribution is allowed if no charges are taken and no changes
are made. This means no comments where you could get this and
other nice programs too!
I have made this program with care and tested it carefully. But I
will take no responsibility for things it does or not does to you
or your computer because of its use (or even its not-use).
HOW TO USE CHECKTIC?
Obviously it should be started before using TICKer-ST. So put it
into the batchfile you use for processing incoming mail/files at
an appropiate place. CHECKTIC need exectly ONE parameter - the
path to the folder containing your TIC-files.
Example:
checktic.ttp e:\io\prot_in\
If you leave out the last backslash, CHECKTIC won't complain and
add it internally. That's all ... :-)
BUT BE CAREFULL: CHECKTIC doesn't check the parameter about being
useful or the existence of the folder. I don't guarantee for the
reaction of CHECKTIC, if you call it with
"Here_I_have_my_TIC-files" - it is YOU responsible that there is
a folder with this name (good luck).
CHECKTIC looks into the folder for TIC-files and checks the
CRC-line for checksums with leading zeros. These files will be
overwritten with the corrected checksum. If you then run
TICKer-ST, it should complain about really bad CRC- checksums.
CHECKTIC will give back the following return-values, so you could
react in run-time within your batchfile:
0 - everything ok
this could mean: - no TIC-files found
- all TIC-files were ok
- one ore more files were corrected
- some TIC-files couldn't been processed
(see LIMITATIONS)
1 - wrong number of parameters or parameter too long
2 - insufficient memory for internal buffer
CHECKTIC uses 64KB for an internal buffer - if you don't have
this amount of memory free left, you're in trouble deep ...
LIMITATIONS:
The current version has some limitations:
- TIC-files with a size of >64 KB are not processed because the
program uses a static buffer of this size. Such monster-TICs
I've never seen here, but who knows... If needed I can change
it by increasing the size of the static buffer or switching the
program to "dynamic" buffering. Please contact me, if you need
this.
- As written above CHECKTIC doesn't check the path-parameter you
started the program with. For this little program I thought
this would be too much work. As you usually use this program
within a batchfile this seems not to be too much trouble for
you.
Done ... the work's done - and the doc probably longer than the
program itself ...
Berlin, Oct. 1st, 1994
Version 1.0.1 (Oct 4th):
bugfix: check for trailing backslash pointed to the '\0' insted
of the last character of the parameter-string -> fixed